Skip to content

packaging: the guided set-up knows the backfill - #154

Merged
EnzinoBB merged 1 commit into
masterfrom
packaging/setup-backfill
Nov 2, 2026
Merged

EnzinoBB merged 1 commit into
masterfrom
packaging/setup-backfill

Conversation

@EnzinoBB

@EnzinoBB EnzinoBB commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator

The set-up (#131) predates the backfill: it told a full node started from a snapshot that it holds only the snapshot's blocks, defaulted full nodes to a sync from block 0, told a pruned folder to start over to become full, and never wrote backfill.

  • Full node on lmdb/rocksdb: first start defaults to the snapshot (GitHub), and question 3b asks whether to fetch the older blocks in the background (writes backfill=on/off; when not asked, an earlier backfill=off is kept; backfill_* tuning keys set by hand are kept).
  • A pruned folder chosen as full keeps its blocks and fetches the removed ones (backfill), instead of being told to start over.
  • The summary shows the backfill choice. Berkeleydb full nodes still sync from block 0 (not asked).
  • setup.sh and setup.ps1 alike; setup-test.yml: a full rocksdb set-up with and without the backfill (tuning key kept), and a pruned folder switched to full.

🤖 Generated with Claude Code

A full node on lmdb or rocksdb now starts from a snapshot by default and
is asked whether to fetch the older blocks in the background (writes
backfill=on/off; a choice made before is kept when not asked, and the
backfill_* keys set by hand are kept). A pruned folder chosen as full
keeps its blocks and fetches the ones it removed. The set-up used to say
that a full node from a snapshot holds only the snapshot's blocks, and
defaulted full nodes to a sync from block 0. setup.sh and setup.ps1
alike; setup-test covers a full rocksdb set-up with and without the
backfill and a pruned folder switched to full.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@EnzinoBB
EnzinoBB merged commit 95075f2 into master Nov 2, 2026
25 of 28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant